Techniques for remotely controlling a medical device based on image data

ABSTRACT

A system and a method for remotely controlling a medical device based on image data are disclosed. The system includes a medical device, an image sensor, and a remote caregiver interface. The medical device includes a controller coupled to a communication network. The image sensor is coupled to the communication network and is configured to capture image data. The remote caregiver interface is coupled to the communication network and is configured to display the image data for viewing by a user, receive a selected remote control function from the user, and transmit an input signal corresponding to the selected remote control function to the controller of the medical device to execute the selected remote control function based on the input signal.

CROSS-REFERENCE TO RELATED APPLICATIONS

The subject patent application is a Continuation of U.S. patentapplication Ser. No. 17/236,385, filed on Apr. 21, 2021, which is aContinuation of U.S. patent application Ser. No. 16/864,354 filed on May1, 2020 and issued as U.S. Pat. No. 11,011,272 on May 18, 2021, which isa Continuation of U.S. patent application Ser. No. 16/211,929 filed onDec. 6, 2018 and issued as U.S. Pat. No. 10,679,748 on Jun. 9, 2020,which claims priority to all the benefits of U.S. Provisional PatentApplication No. 62/609,809 filed on Dec. 22, 2017, the disclosures ofeach of which are hereby incorporated by reference in their entirety.

BACKGROUND

Remote control functions may be used to control a medical devices from aremote location. Such medical devices may include, for example, patientsupport apparatuses, such as hospital beds, stretchers, cots, tables,wheelchairs, recliners, and chairs for patient care. Other medicaldevices may include equipment such as lights, televisions, temperaturemanagement systems, respirators, IV lines, surgical tools, and heartrate monitors that may be used in medical procedures or in the provisionof medical services to patients. For example, a remote control functionmay incline a back section of the patient support apparatus, activate aspeaker of the patient support apparatus, adjust a height of the patientsupport apparatus, engage a side rail of the patient support apparatus,and/or provide turning assistance by the patient support apparatus. Theremote control functions may be in response to patient requests.

Typically, remote control functions may be initiated by a caregiver whois assigned to the patient or the patient support apparatus, but is notin the same room or near the patient. Therefore, due to the nature of aremote control function, caregivers may not be able to interact with orview their patients prior to or during an execution of a remote controlfunction. The patient's comfort or safety may therefore be inadvertentlycompromised by the execution of the remote control function. As such,there are opportunities to address at least the aforementioned problems.

BRIEF DESCRIPTION OF THE DRAWINGS

Advantages of the present disclosure will be readily appreciated as thesame becomes better understood by reference to the following detaileddescription when considered in connection with the accompanyingdrawings.

FIG. 1 is a perspective view of a system including a patient supportapparatus, a controller, a remote caregiver interface, and an imagesensor;

FIG. 2 is a schematic diagram illustrating the controller, the remotecaregiver interface, and the image sensor;

FIG. 3A is a flowchart illustrating a method for remotely controllingthe patient support apparatus based on image data, which includes a stepof selecting and executing a remote control function and a step ofautomatically altering the remote control function based on a patientcondition;

FIG. 3B is a flowchart illustrating the step of selecting and executingthe remote control function;

FIG. 3C is a flowchart illustrating the step of automatically alteringthe remote control function based on the patient condition;

FIG. 4 is a flowchart illustrating a second embodiment of the method,which includes a step of determining the patient condition before thestep of selecting and executing the remote control function;

FIG. 5A is a flowchart illustrating a third embodiment of the method,which includes a step of providing a patient sensor, the step ofselecting and executing the remote control function, and a step ofautomatically altering the remote control function based on the patientcondition;

FIG. 5B is a flowchart illustrating the step of automatically alteringthe remote control function based on the patient condition of the thirdembodiment of the method;

FIG. 6 is a flowchart illustrating a fourth embodiment of the method,which includes the step of determining the patient condition before thestep of selecting and executing the remote control function;

FIG. 7 is a schematic diagram illustrating the remote caregiverinterface, a local user interface, the image sensor, and a speaker ofthe patient support apparatus;

FIG. 8 is a flowchart illustrating a method of initiating a videoconference based on the patient condition; and

FIG. 9 is a view of an embodiment of the remote caregiver interface.

DETAILED DESCRIPTION

Referring to the Figures, wherein like numerals indicate like orcorresponding parts throughout the several views, techniques forremotely controlling medical devices based on image data are provided.

A system for remotely controlling a medical device based on image datais disclosed. The system includes a medical device including acontroller coupled to a communication network. The system also includesan image sensor coupled to the communication network and beingconfigured to capture image data an area including the medical device.Additionally, the system includes a remote caregiver interface coupledto the communication network. The remote caregiver interface isconfigured to display the image data, receive a selected remote controlfunction from the user, and transmit an input signal to the controllerof the medical device to execute the selected remote control function.

The system may remotely control a variety of medical devices based onimage data. For example, in one embodiment, the system may remotelycontrol a temperature management device, such as a blanket warmingdevice, based on image data. In such an embodiment, the blanket warmingdevice may be configured to warm a blanket placed on a patient based onimage data. For example, the system may remotely control the blanketwarming device to warm the blanket based on a temperature of thepatient, a temperature of a hospital room, or a temperature of a patientsupport apparatus of a hospital room, which may be determined based oninfrared image data.

In another embodiment, the system may remotely control an intravenoustherapy device based on a condition of the patient, which may bedetermined based on image data of the patient. For example, in oneembodiment, the system may control the intravenous therapy device todeliver fluids or medications to the patient based a patient presence, acomfort indication of the patient, or a physiological state of thepatient. In one such embodiment, the intravenous therapy device may beconfigured to deliver fluids to a patient with a fever.

In other embodiments, the system may remotely control other medicaldevices based on image data. For instance, the system may remotelycontrol medical devices such as, but not limited to, a heart ratemonitor, a medical ventilator device, a light in a hospital room, atelevision in a hospital room, or any other such medical device.

In the embodiment of FIG. 1 , the medical device is a patient supportapparatus 100 for supporting a patient in a health care setting. Thepatient support apparatus 100 illustrated in FIG. 1 includes a hospitalbed. However, in other embodiments, the patient support apparatus 100may include a stretcher, a cot, a table, a wheelchair, a recliner, achair for patient care, or any other similar apparatus utilized in thecare of a patient.

A support structure 110 provides support for the patient. The supportstructure 110 illustrated in FIG. 1 includes a base 150 and a supportframe 130. The base 150 includes a base frame 151. The support frame 130is spaced above the base frame 151 in FIG. 1 . The support structure 110also includes a patient support deck 140 disposed on the support frame130. The patient support deck 140 includes several sections, some ofwhich are capable of articulating relative to the support frame 130,such as a back section, a seat section, a thigh section, and a footsection. The patient support deck 140 provides a patient support surface141 upon which the patient is supported.

A mattress 160 may be disposed on the patient support deck 140 duringuse. The mattress 160 includes a secondary patient support surface 161upon which the patient is supported. In addition, the mattress 160 maybe omitted in certain embodiments, such that the patient rests directlyon the patient support surface 141.

The base 150, support frame 130, patient support deck 140, and patientsupport surface 141 each have a head end and a foot end corresponding toa designated placement of the patient's head and feet on the patientsupport apparatus 100. The construction of the support structure 110 maytake on any suitable design, and is not limited to that specifically setforth above.

Side rails 171, 172, 173, 174 are coupled to the support frame 130 orthe patient support deck 140 and are thereby supported by the base 150.A first side rail 171 is positioned at a left head end of the patientsupport deck 140. A second side rail 172 is positioned at a left footend of the support frame 130. A third side rail 173 is positioned at aright head end of the patient support deck 140. A fourth side rail 174is positioned at a left foot end of the support frame 130. If thepatient support apparatus 100 is a stretcher or a cot, there may befewer side rails. The side rails 171, 172, 173, 174 are movable to araised position in which they block ingress and egress into and out ofthe patient support apparatus 100, one or more intermediate positions,and a lowered position in which the side rails 171, 172, 173, 174 arenot an obstacle to such ingress and egress. In still otherconfigurations, the patient support apparatus 100 may not include anyside rails.

A headboard 181 and a footboard 182 are coupled to the support frame130. In other embodiments, when the headboard 181 and footboard 182 areincluded, the headboard 181 and footboard 182 may be coupled to otherlocations on the patient support apparatus 100, such as the base 150. Instill other embodiments, the patient support apparatus 100 does notinclude the headboard 181 and/or the footboard 182.

Caregiver interfaces 183, such as handles, are shown integrated into thefootboard 182 and side rails 171, 172, 173, 174 to facilitate movementof the patient support apparatus 100 over floor surfaces. Additionalcaregiver interfaces 183 may be integrated into the headboard 181 and/orother components of the patient support apparatus 100. The caregiverinterfaces 183 are graspable by a caregiver to manipulate the patientsupport apparatus 100 for movement.

Wheels 190 are coupled to the base 150 to facilitate transport over thefloor surfaces. The wheels 190 are arranged in each of four quadrants ofthe base 150 adjacent to corners of the base 150. In the embodimentshown, the wheels 190 are caster wheels able to rotate and swivelrelative to the support structure 110 during transport. Each of thewheels 190 forms part of a caster assembly 192. Each caster assembly 192is mounted to the base 150. It should be understood that variousconfigurations of the caster assemblies 192 are contemplated. Inaddition, in some embodiments, the wheels 190 are not caster wheels andmay be non-steerable, steerable, non-powered, powered, or combinationsthereof. Additional wheels are also contemplated. For example, thepatient support apparatus 100 may include four non-powered,non-steerable wheels, along with one or more powered wheels. In somecases, the patient support apparatus 100 may not include any wheels.

In other embodiments, one or more auxiliary wheels (powered ornon-powered), which are movable between stowed positions and deployedpositions, may be coupled to the support structure 110. In some cases,when these auxiliary wheels are located between caster assemblies 192and contact the floor surface in the deployed position, they cause twoof the caster assemblies 192 to be lifted off the floor surface therebyshortening a wheel base of the patient support apparatus 100. A fifthwheel may also be arranged substantially in a center of the base 150.

As shown in FIG. 1 , the system 10 may include an actuatable device 120and actuators 121, 122. The actuators 121, 122 may be further defined asbeing capable of moving the actuatable device 120. The actuators 121,122 may be coupled to the support structure 110 to move the patient whenthe patient is disposed on the patient support structure 110. In theembodiment of the patient support apparatus 100 shown in FIG. 1 , thepatient support apparatus 100 includes two actuators 121, 122. However,it is to be noted that the patient support apparatus 100 may include anysuitable number of actuators 121, 122. Furthermore, any of thetechniques described herein can utilize any number of actuators 121, 122individually or in combination.

The actuators 121, 122 should be broadly understood as a type of motoror device that is capable of moving or controlling a mechanism or asystem. For example, some suitable, non-limiting examples of theactuators 121, 122 are mechanical, hydraulic, pneumatic, electric,thermal, or magnetic actuators. The actuators 121, 122 may also includemotors, such as a rotational or linear motor. In a further example, theactuators 121, 122 may include an inflation actuator. In sum, it shouldbe understood that any type of actuator can be used in certainapplications.

As described above, the actuators 121, 122 may be further defined asbeing capable of moving an actuatable device 120. These actuatabledevices 120 are not particularly limited, and may include any device orsystem that includes one or more actuators 121, 122. In certainembodiments, the actuatable device 120 is one that, when actuated,results in a change of position of the patient support surfaces 141, 161of the patient support structure 110. This change in position of one ormore patient support surfaces 141, 161 when the patient occupies thepatient support apparatus 100, results in a change in the position ofone or more portions of the patient's body.

More specifically, in situations where a patient occupies the patientsupport apparatus 100, i.e., contacts one or more patient supportsurfaces 141, 161, operation of each of the actuatable devices 120results in movement of one or more portions of the patient in one ormore dimensions relative to a static surface, such as relative to afloor of a hospital. Examples of such movement include, but are notlimited to: forward and reverse movement of the patient by virtue ofmovement of the patient support structure 110 along a floor; raising andlowering movement of the patient by virtue of movement of the patientsupport structure 110 upward and downward relative to the floor; angularmovement by virtue of changing the angle of at least a portion of thepatient support structure 110 relative to a floor; rotation of thepatient along a longitudinal axis of the patient support structure 110(while the patient support apparatus 100 remains stationary relative tothe floor); or various combinations of those types of movement.

Without limitation, the actuatable devices 120 that result in the changeof the position of one or more patient support surfaces 141, 161 of thepatient support structure 110 may include a coordinated motion device, apatient raising device, a patient turning device, a patient centeringdevice, a patient ingress/egress device, a lift device, a fowleradjustment device, a patch adjustment device, a side rail engagementdevice, and a transport device.

It is also contemplated that the actuatable device 120 may be of thetype that does not result in a change of position, orientation, and/orelevation of the patient support surfaces 141, 161. These “non-positionactuatable devices” may include, but are not limited to, a patientcomfort device, such as an entertainment device, a lighting device, atemperature device, a humidity device, and an aromatherapy device, aswell as patient therapy devices, such as vibration therapy devices,percussion therapy devices, compression therapy devices, patient warmingdevices, and electrical stimulation devices. The rate of operation ofthese non-position actuatable devices can also be controlled by changingthe frequency, tempo, rate of temperature change, rate of humiditychange, intensity of therapy, etc. of the devices.

The patient support apparatus 100, as shown in FIG. 1 , also includes acontroller 195. In FIG. 1 , the controller 195 is illustrated as beingdisposed within the footboard 182. However, in other embodiments, thecontroller 195 may be disposed on or within the headboard 181, the siderails 171, 172, 173, 174, the caregiver interfaces 183, or any othersuitable component of the patient support apparatus 100.

The system 10 may also include an image sensor 193 for capturing imagedata of an area including the patient support apparatus 100, referred toherein as the “patient support apparatus image data”. In the embodimentshown in FIG. 1 , the image sensor 193 may be included as part of asurveillance camera. However, in other embodiments, the image sensor maybe included as part of any device suitable for capturing the patientsupport apparatus image data, such as a digital camera, a thermographiccamera, a webcam, a video camera, a livestream broadcast camera, aninfrared image sensor, or combinations thereof. Accordingly, the patientsupport apparatus image data may vary according to the image sensor 193.For example, if the image sensor 193 is a digital camera, the patientsupport apparatus image data may be a photo. In another example, if theimage sensor 193 is a video camera, the patient support apparatus imagedata may be a video. In yet another example, if the image sensor 193 isa thermographic camera, the patient support apparatus image data may bethermal image data.

Furthermore, as shown in FIG. 1 , the image sensor 193 is coupled to awall of the hospital room. In other embodiments, the image sensor 193may be located in any location on a medical device or in any locationsuitable for capturing the patient support apparatus image data. Forexample, in other embodiments, the image sensor 193 may be mounted to aceiling of the hospital room, a floor of the hospital room, or a supportstructure of the hospital room. In other embodiments, the image sensor193 may be coupled to the patient support apparatus 100. For example,the image sensor 193 may be disposed on or within the headboard 181, thefootboard 182, any of the side rails 171, 172, 173, 174, the caregiverinterfaces 183, or any other suitable component of the patient supportapparatus 100.

The system 10 may also include a remote caregiver interface 198 for useby a caregiver 196. In the embodiment shown in FIG. 1 , the remotecaregiver interface 198 is a tablet device. However, the remotecaregiver interface 198 may be any suitable remote computing device. Forexample, the remote caregiver interface 198 may be any one of a desktopcomputer or a nurse call station. In other embodiments, the remotecaregiver interface may be any suitable mobile computing device such asa cellular phone, a laptop, or a wearable remote device.

In some embodiments, the remote caregiver interface 198 may include acamera for capturing image data, referred to herein as the “caregiverimage data”. For example, the caregiver image data may be of thecaregiver 196 or a face of the caregiver 196. Furthermore, the camerafor capturing the caregiver image data may be any suitable camera, suchas a digital camera, a thermographic camera, a webcam, a video camera, alivestream broadcast camera, or any other device suitable for capturingthe caregiver image data. Additionally, the camera for capturing thecaregiver image data may be disposed on or within the remote caregiverinterface 198. Such features may allow the patient to see the face ofthe caregiver who is controlling their patient support apparatus 100.

In some embodiments, the remote caregiver interface 198 may include amicrophone for capturing audio data, referred to herein as the“caregiver audio data”. For example, the caregiver audio data may be avoice of the caregiver 196. Furthermore, the microphone for capturingthe caregiver audio data may be any suitable microphone, such as acondenser microphone, a dynamic microphone, a piezoelectric microphone,an electret microphone, a wireless microphone, or a wearable microphone.Additionally, the microphone for capturing the caregiver audio data maybe disposed on or within the remote caregiver interface 198. Suchfeatures may allow the patient to hear the voice of the caregiver 196who is controlling their patient support apparatus 100.

The remote caregiver interface 198 may be configured to display agraphical user interface. One example of the remote caregiver interface198 and the graphical user interface is illustrated in FIG. 9 .

It should be noted that, while the embodiment shown in FIG. 1 includesone remote caregiver interface 198, the system 10 may include anysuitable number of remote caregiver interfaces 198. For example, in someembodiments, the system 10 may also include a second remote caregiverinterface for use by a second caregiver and a third remote caregiverinterface for use by a third caregiver.

Furthermore, the system 10 may be designed to be used by any suitablenumber or types of caregivers 196. For example, the system 10 may beused by a first caregiver, who may be the caregiver initially assignedto the patient or the patient's primary caregiver. In some embodiments,the system 10 may also designate a second caregiver as a backupcaregiver to the first caregiver. In other embodiments, the secondcaregiver may be chosen from a group of available caregivers. The system10 may also appoint a master caregiver, who may be assigned to monitormultiple patients. For example, the third caregiver may be a nurse whois assigned to the nurse call station or who is assigned to monitormultiple patients at a local or remote command center. Of course, thesystem 10 may be designed for use by more than two caregivers, and mayinclude any suitable number of remote caregiver interfaces 198.

The system 10 may also include a local user interface 194. In someembodiments, the local user interface 194 may be disposed on the patientsupport apparatus 100. For example, the local user interface 194 may bea user interface of the patient support apparatus 100 such as atouchscreen of the patient support apparatus 100, buttons of the patientsupport apparatus 100, or switches of the patient support apparatus 100.

In other embodiments, the local user interface 194 may be separated fromthe patient support apparatus 100. For example, the local user interface194 may be mounted to a ceiling of a hospital room, a support structureof the hospital room, or a wall of the hospital room. In anotherexample, the local user interface 194 may be a mobile computing device.For example, the local user interface 194 may be any one of a cellularphone, a laptop, a wearable remote device, a tablet (as shown in theembodiment of FIG. 1 ), or any other suitable mobile input device.

The local user interface 194 may be configured to display a graphicaluser interface. In embodiments where the remote caregiver interface 198may also be configured to display a graphical user interface, thegraphical user interface of the local user interface 194 may beidentical to the graphical user interface of the remote caregiverinterface 198. In other embodiments, the local caregiver interface 194may replicate at least a portion of the graphical user interface of theremote user interface 198.

In some embodiments, the local user interface 194 may include a camerafor capturing image data, referred to herein as the “user image data”.For example, the user image data may be of the patient, a face of thepatient, a person within a vicinity of the patient support apparatus100, or the patient support apparatus 100 itself. Furthermore, thecamera for capturing the user image data may be any suitable camera,such as a digital camera, a thermographic camera, a webcam, a videocamera, a livestream broadcast camera, or any other device suitable forcapturing the caregiver image data. Additionally, the camera forcapturing the user image data may be disposed on or within the localuser interface 194. Such features may allow the caregiver 196 to see thepatient in the patient support apparatus 100 while the caregiver 196controls the patient support apparatus 100.

In some embodiments, the local user interface 194 may include amicrophone for capturing audio data, referred to herein as the “useraudio data”. For example, the audio data may be a voice of the patientor a voice of a person within the vicinity of the patient supportapparatus 100. Furthermore, the microphone for capturing the user audiodata may be any suitable microphone, such as a condenser microphone, adynamic microphone, a piezoelectric microphone, an electret microphone,a wireless microphone, or a wearable microphone. Additionally, themicrophone for capturing the caregiver audio data may be disposed on orwithin the local user interface 194. Such features may allow thecaregiver 196 to hear the voice of the patient while the caregiver 196controls the patient support apparatus 100.

Furthermore, it should be noted that, in various embodiments, the localuser interface 194 may be defined differently. For example, in anembodiment where the local user interface 194 is disposed on the patientsupport apparatus 100, the local patient interface may be defined asbeing used by a person adjacent to or disposed on the patient supportapparatus 100. However, in embodiments where the local user interface194 is separated from the patient support apparatus 100, the local userinterface 194 may be defined as being used by a person within thevicinity of the patient support apparatus 100. The person within thevicinity of the patient support apparatus 100 may be any one of thepatient, a caregiver, a family member, a hospital staff member, or anyother suitable person. However, in different embodiments, the vicinityof the patient support apparatus 100 may be defined differently. Forexample, in one embodiment, the local user interface 194 may be definedas being used by the patient disposed on the patient support apparatus100. In another embodiment, the local user interface 194 may be definedas being used by a person within 50 feet of the patient supportapparatus 100. In yet another embodiment, the local user interface 194may be defined as being used by a person in the same room as the patientsupport apparatus 100.

The patient support apparatus 100 may also include a patient sensor 197.In FIG. 1 , the sensing system 197 is illustrated as being disposedwithin the fourth side rail 174. However, in other embodiments, thepatient sensor 197 may be disposed on or within the headboard 181, thefootboard 182, any of the side rails 171, 172, 173, 174, the caregiverinterfaces 183, or any other suitable component of the patient supportapparatus 100.

The patient sensor 197 may include a variety of sensors for sensing astate of the patient. For example, the patient sensor 197 may include aheart rate sensor, a patient temperature sensor, a moisture sensor, ashear sensor, a neurological sensor, a load cell, a blood pressuresensor, a camera, a force sensor, a breathing monitor, a patientexpression sensor, a patient acoustic sensor, a scale, a switch, anoptical sensor, an infrared sensor, an electromagnetic sensor, anaccelerometer, a potentiometer, an ultrasonic sensor, or combinationsthereof for sensing the state of the patient.

As shown in FIG. 1 , the controller 195, the remote caregiver interface198, and the image sensor 193 may be coupled to a communication network191 to communicate wirelessly with one another. The communicationnetwork 191 may be any suitable communication network. For example, thecommunication network 191 may include any one of Bluetooth, WiFi,Infrared, ZigBee, radio waves, cellular signals, any other suitablecommunication network, or combinations thereof. In some embodiments, thecommunication network 191 may include a networking device such as agateway device, a router, or a repeater. In other embodiments, thecontroller 195, the remote caregiver interface 198, and the image sensor193 may communicate with each other using peer-to-peer communication.

FIG. 2 features a schematic diagram which further illustrates thecommunication network 191. In the embodiment shown in FIG. 2 , thecontroller 195, the image sensor 193, the remote caregiver interface198, the local user interface 194, and the patient sensor 197 may becoupled to one another via the communication network 191.

For example, as shown in FIG. 2 , the controller 195 may be coupled tothe remote caregiver interface 198 via the communication network 191 andmay receive an input signal corresponding to a selected remote controlfunction from the remote caregiver interface 198, referred to herein asthe “remote input signal”. The controller 195 may also be coupled to thelocal user interface 194 via the communication network 191 and mayreceive another input signal corresponding to a selected local controlfunction from the local user interface 194, referred to herein as the“local input signal”. Furthermore, the controller 195 is also coupled tothe actuators 121, 122 of the patient support apparatus 100 and maytransmit an output signal to the actuators 121, 122 to cause movement ofthe one or more actuatable devices 120 based on the remote input signalor the local input signal.

It should be noted that, in some embodiments, the controller 195 may becoupled to the local user interface 194 without using the communicationnetwork 191. For example, in an embodiment where the local userinterface 198 is the user interface of the patient support apparatus100, the local user interface 198 may be in direct communication withcontroller 195. As such, the controller 195 may receive the selectedlocal control function without using the communication network 191.

As previously stated, the remote input signal corresponds to theselected remote control function from the remote caregiver interface198. The selected remote control function may be categorized as anon-patient remote control function or a patient remote controlfunction. A remote control function is categorized as a patient remotecontrol function if the remote control function causes movement of thepatient support apparatus 100, causes movement of one or more actuatabledevices 120 that are configured to move a patient or contact a patient,or could result in a change of state of the patient support apparatus100 that could have adverse consequences for the patient. For example, apatient remote control function may cause the actuator 121, 122 to liftthe side rails 171, 172, 173, 174, apply a brake of the patient supportapparatus 100, lift the patient support deck 140, or incline the backsection (i.e., the head end) of the patient support deck 140. Incontrast, a non-patient remote control function does not cause movementof the patient support apparatus 100. For example, a non-patient remotecontrol function may cause the controller 195 to activate a speaker 185of the patient support apparatus 100 to play music, activate one or morelights of the patient support apparatus 100, or activate othercomponents of the patient support apparatus 100 which are unrelated tomovement.

Also previously stated, the local input signal corresponds to theselected local control function from the local user interface 198.Similarly, the selected local control function may be categorized as anon-patient local control function or a patient local control function.More explicitly stated, a local control function may also be categorizedas a patient local control function if the local control function causesmovement of the patient support apparatus 100, causes movement of one ormore actuatable devices 120 that are configured to move a patient orcontact a patient, or could result in a change of state of the patientsupport apparatus 100 that could have adverse consequences for thepatient.

In some embodiments, the selected local control function may overridethe selected remote control function. For example, in an embodimentwhere the controller 195 receives the remote input signal from theremote caregiver interface 198 and then receives the local input signalfrom the local user interface 194, the controller may abort the selectedremote control function and execute the selected local control function.In an embodiment where the controller 195 receives the local inputsignal from the local user interface 194 and then receives the remoteinput signal from the remote caregiver interface 198, the remote controlfunction may ignore the selected remote control function and execute theselected local control function. In another embodiment, the local inputsignal may cause the controller to abort the selected remote controlfunction and return the patient support apparatus 100 to its initialstate. Alternatively, the selected remote control function may overridethe selected local control function in a similar manner as describedabove.

In other embodiments, the selected local control function and theselected remote control function may both be executed. For example, inone embodiment, the controller 195 may execute both the selected remotecontrol function and the selected local control function if no conflictexists. In an example embodiment, the selected local control functionmay cause the controller 195 to activate the speaker 185 to play musicwhile the selected remote control function causes the actuators 121, 122to lift the side rails 171, 172, 173, 174.

As shown in FIG. 2 , the remote caregiver interface 198 and thecontroller 195 may be coupled to the image sensor 193 via thecommunication network 191 and may receive the patient support apparatusimage data from the image sensor 193.

Also shown in FIG. 2 , the remote caregiver interface 198 may be coupledto the local user interface 194 and may transmit the caregiver imagedata and the caregiver audio data to the local user interface 194 viathe communication network 191. Similarly, the local user interface 194may transmit the user image data and the user audio data to the remotecaregiver interface 198.

In some embodiments, the controller 195 may be coupled to the imagesensor 193 without using the communication network 191. For example, inan embodiment where the image sensor 193 is disposed within the patientsupport apparatus 100, the image sensor 193 and the controller 195 maybe in direct communication with each other. As such, the controller 195may receive the patient support apparatus image data without the use ofthe communication network 191.

Also shown in FIG. 2 , the controller 195 and the remote caregiverinterface 198 may be coupled to the patient sensor 197 via thecommunication network 191 and may receive a sensor input signal from thepatient sensor 197. The patient sensor 197 may transmit the sensor inputsignal representing the state of the patient. For example, the sensorinput signal may include a heart rate of the patient, a temperature ofthe patient, a moisture level of the patient support apparatus 100, aweight of the patient, a blood pressure of the patient, vital signs ofthe patient, and any other sensed parameter that may indicate the stateof the patient.

In some embodiments, the controller 195 may be coupled to the patientsensor 197 without using the communication network 191. For example, inthe embodiment shown in FIG. 1 , the patient sensor 197 is disposedwithin the patient support apparatus 100. In such an embodiment, thepatient sensor 197 and the controller 195 may be in direct communicationwith each other. As such, the controller 195 may receive the sensorinput signal from the patient sensor 197 without the use of thecommunication network 191.

Additionally, as shown in FIG. 2 , the controller 195 includes a memory203 and a processor 202. The processor 202 may be any processor suitablefor processing data. For example, the processor 202 may be a processortypically found in a desktop computer or a processor typically found ina mobile processing device such as a cellular phone, a tablet, or alaptop. Similarly, the memory 203 may be any memory suitable for storageof data and computer-readable instructions. For example, the memory 203may be a local memory, an external memory, or a cloud-based memoryembodied as random access memory (RAM), non-volatile RAM (NVRAM), flashmemory, or any other suitable form of memory.

To further aid in understanding the system 10, FIG. 3A provides aflowchart illustrating a method of remotely controlling the patientsupport apparatus 100 based on image data. As shown in FIG. 3A, themethod may include a step 300 of providing the remote caregiverinterface 198, the image sensor 193, and the patient support apparatus100. The method may also include a step 310 of selecting and executingthe remote control function and a step 320 of automatically altering theremote control function based on a patient condition. Also shown in FIG.3A, step 320 may include a step 330 of determining the patientcondition.

Step 320 is further illustrated in FIG. 3B. As shown, the method mayinclude a step 311 of capturing the patient support apparatus imagedata, a step 312 of transmitting the patient support apparatus imagedata to the remote caregiver interface 198, and a step 313 of receivingthe selected remote control function from a user of the remote caregiverinterface 198. In one embodiment, the image sensor 193 may perform steps311 and 312 and the remote caregiver interface 198 may perform step 313.Additionally, it should be noted that the user of the remote caregiverinterface 198, such as the caregiver 196, is able to view the patientsupport apparatus image data once it is transmitted and received by theremote caregiver interface 198. As such, the user of the remotecaregiver interface 198 is able to select the remote control functionbased on the patient support apparatus image data. Of course, in someembodiments, the user of the remote caregiver interface 198 may selectthe remote control function without viewing the patient supportapparatus image data or before the patient support apparatus image datais transmitted to or received by the remote caregiver interface 198.

An example embodiment may be used to further explain the method and maybe referred to herein as the “foot section elevation embodiment”. In thefoot section elevation embodiment, the patient support apparatus imagedata captured during step 311 and transmitted during 312 may indicatethat the patient is experiencing swelling in their legs. As a result,the caregiver 196 may use the remote caregiver interface 198 to select aremote control function during step 313 which, when executed, causes theactuators 121, 122 to elevate the foot section of the patient supportdeck 140, reducing the swelling in the patient's legs. This remotecontrol function may be described herein as the “foot section elevationremote control function”.

After receiving the selected remote control function during step 313,the method proceeds to a step 314 of transmitting the input signalcorresponding to the remote control function, i.e. the remote inputsignal, to the controller 195 of the patient support apparatus 100. Themethod then continues to a step 315 of transmitting an output signal tothe actuators 121, 122 of the patient support apparatus 100 to executethe remote control function. In one embodiment, the remote caregiverinterface 198 may perform step 314 and the controller 195 may performstep 315. In the foot section elevation embodiment, the remote caregiverinterface 198 transmits the input signal corresponding to the footsection elevation remote control function during step 314. Accordingly,the controller 195, during step 315, transmits the output signal to theactuators 121, 122 of the patient support apparatus 100, which elevatesthe foot section of the patient support deck 140.

Referring back to FIG. 3A, after the remote control function is selectedand executed during step 310, the method may proceed to step 320 wherethe method determines the patient condition during step 330 andautomatically alters the selected remote control function based on thepatient condition. During step 320, the method may automatically alterthe selected remote control function by automatically aborting theselected remote control function, modifying the selected remote controlfunction, or selecting a new remote control function. Furthermore, themethod may automatically alter the selected remote control functionwhile the selected remote control function is being executed. Forexample, in the foot section elevation embodiment, the method may abortthe foot section elevation remote control function during step 320 andcease elevation of the foot section of the patient support deck 140. Asanother example, the method may modify the foot section elevation remotecontrol function during step 320 by elevating the foot section of thepatient support deck 140 at a slower speed. As yet another example, themethod may select a different remote control function during step 320 bycausing the actuators 121, 122 to incline the back section of thepatient support deck 140 instead of elevating the foot section of thepatient support deck 140.

The method may also automatically alter a patient therapy protocolduring step 320. In some embodiments, the remote control function may befurther defined as a patient therapy protocol. As previously discussed,the remote control function may be categorized as a non-patient remotecontrol function or a patient remote control function. The patientremote control function may be further categorized as a discrete patientremote control function or a periodic patient remote control function.As used herein, a discrete patient remote control function causes thecontroller 195 to execute a singular command. For example, a discretepatient remote control function may cause the actuators 121, 122 to liftthe patient support deck 140 or incline the back section of the patientsupport deck 140 a single instance. As used herein, a periodic patientremote control function causes the controller 195 to execute a singularcommand periodically. For example, a periodic patient remote controlfunction may cause the actuators 121, 122 to elevate a foot section ofthe patient support deck 140 every hour. The patient therapy protocol isan example of a periodic patient remote control function. The patienttherapy protocol may be defined as including a set of desiredtherapeutic actions which cause movement of one or more actuatabledevices 120 to provide therapy to the patient and may be periodicallyexecuted during “instances” of the patient therapy protocol. Forexample, in one embodiment of the patient therapy protocol, the patienttherapy protocol may cause the actuators 121, 122 to turn the patientevery half hour to reduce a risk of acquiring pressure ulcers. As usedherein, this embodiment of the patient therapy protocol may be referredto as the “patient turning embodiment” and the corresponding patienttherapy protocol may be referred to as the “patient turning therapyprotocol”.

In an embodiment where the selected remote control function is a patienttherapy protocol, the method may automatically alter the patient therapyprotocol at any time during the patient therapy protocol. Moreexplicitly stated, the method may automatically abort, modify, or selecta different remote control function before, during, or after anyinstance of the patient therapy protocol. For example, in the patientturning embodiment, the method may abort the patient turning therapyprotocol during step 320 and cease turning the patient. As anotherexample, the method may modify the patient turning therapy protocolduring step 320 by turning the patient at a faster speed. As yet anotherexample, the method may select a different remote control functionduring step 320 by causing the actuators 121, 122 to elevate the footsection of the patient support deck 140 every hour or by causing theactuators 121, 122 to incline the back section of the patient supportdeck. Furthermore, in the patient turning embodiment, the method mayautomatically alter the patient therapy protocol before the actuators121, 122 turn the patient, while the actuators 121, 122 are turning thepatient, and after the actuators 121, 122 turn the patient.

Step 320 is further shown in FIG. 3C. As previously discussed, step 320includes the step 330 of determining the patient condition. As shown,step 330 includes the step 311 of capturing the patient supportapparatus image data. Step 330 may also include a step 312′. Step 312′is similar to step 312 because, during both steps, the method transmitsthe patient support apparatus image data to the remote caregiverinterface 198. However, during step 312′, the method may also transmitthe patient support apparatus image data to the controller 195. In oneembodiment, the image sensor 193 may perform steps 311 and 312′.

As shown in FIG. 3C, step 330 may also include the step 316 of analyzingthe patient support apparatus image data to determine the patientcondition. The patient condition may include a patient presence, acomfort indication of the patient, a physiological state of the patient,or combinations thereof. For example, in the patient turning embodiment,the remote caregiver interface 198 and/or the controller 195 may analyzethe patient support apparatus image data and determine that the patientis suffering from nausea. In another example, the remote caregiverinterface 198 and/or the controller 195 may analyze the thermal patientsupport apparatus image data and determine that the patient has a fever.

As previously stated, the patient support apparatus image data is sentto the remote caregiver interface 198 and/or the controller 195 duringstep 312′. As such, the remote caregiver interface 198 and/or thecontroller 195 may perform step 316. In other words, the remotecaregiver interface 198 and/or the controller 195 may analyze thepatient support apparatus image data to determine the patientconditions.

Additionally, it should be noted that the remote caregiver interface 198and the controller 195 may use any suitable image analysis technique todetermine the patient condition. For instance, the remote caregiverinterface 198 and the controller 195 may use edge detection techniques,object recognition techniques, motion detection techniques, and videotracking techniques to analyze the patient support apparatus image dataand determine the patient condition.

After step 316, the method proceeds to a step 317 of automaticallyaltering the selected remote control function based on the patientcondition. As previously described, the method may automatically alterthe selected remote control function by aborting the selected remotecontrol function, modifying the selected remote control function, orselecting a new remote control function. For example, in the patientturning embodiment, the remote caregiver interface 198 and/or thecontroller 195 determines that the patient is suffering from nauseaduring step 316. As follows, the remote caregiver interface 198 and/orthe controller 195 may automatically alter the selected remote controlfunction during step 317 by modifying the patient turning therapyprotocol to turn the patient at a slower rate.

Furthermore, it should be noted that the selected remote controlfunction may be altered based on the patient condition, which may bedetermined by the remote caregiver interface 198 and/or the controller195 during step 330. As such, the remote caregiver interface 198 and/orthe controller 195 may perform step 317. However, in some embodiments,if the remote caregiver interface 198 alters the selected remote controlfunction during step 330, the remote caregiver interface 198 may alsotransmit another input signal to the controller 195 corresponding to thealtered remote control function, referred to herein as the “alteredinput signal”.

After the method alters the selected remote control function based onthe patient condition, the method proceeds to a step 315′ oftransmitting the output signal to the actuators 121, 122 to execute thealtered remote control function. Step 315′ is similar to step 315,except step 315′ transmits the output signal to execute the alteredremote control function instead of the selected remote control function.Just as the controller 195 may perform step 315, the controller 195 mayalso perform step 315′.

Additionally, it should be noted that, during step 315′, the outputsignal may vary depending on how the selected remote control function isaltered during step 317. For example, in the patient turning embodiment,the method may modify the patient turning therapy protocol during step317 to turn the patient at the slower rate. As such, the controller 195transmits the output signal to the actuators 121, 122, causing theactuators 121, 122 to turn the patient at the slower rate during step315′. In an embodiment where the selected remote control function isaborted during step 317, the controller 195 may cease transmission ofthe output signal during step 315′. In an embodiment where a new remotecontrol function is selected during step 317, the controller 195 maytransmit the output signal to the actuators 121, 122 to execute the newremote control function during step 315′.

FIG. 4 is a flowchart illustrating an embodiment of the method where themethod determines the patient condition during step 330 before selectingand executing the remote control function during step 310. In such anembodiment, the patient condition may trigger step 310. For example, inthe patient turning embodiment, after the method determines that thepatient has a high risk of acquiring a pressure ulcer during step 330,the method proceeds to step 310, where the patient support apparatusimage data is captured and transmitted to the remote caregiver interface198 for viewing by the caregiver 196. The caregiver 196 may then selectthe appropriate remote control function, such as the patient turningtherapy protocol, to reduce the patient's risk of acquiring a pressureulcer.

In another embodiment, the patient condition may be presented to theuser of the remote caregiver interface 198 before step 310. As such, theuser of the remote caregiver interface 198 may view the patientcondition before selecting and executing the remote control functionduring step 313. For example, in the foot section elevation embodiment,the method may determine that the patient is experiencing swelling intheir legs and present this patient condition to the caregiver 196. Thecaregiver 196 may then view the patient condition and the patientsupport apparatus image data before selecting the foot section elevationremote control function to reduce the swelling in the patient's leg. Ofcourse, in some embodiments, the patient condition may be presented tothe user of the remote caregiver interface 198 after step 312 of step310, but before 313. In such embodiments, the patient condition may bepresented to the caregiver 196 after the patient support apparatus imagedata is transmitted to the remote caregiver interface 198, but beforethe caregiver 196 selects the remote control function. Furthermore, themethod may also notify the caregiver 196 of the patient condition afterthe method determines the patient condition. The method may notify thecaregiver 196 using a tactile, audio, or visual alert on the remotecaregiver interface 198.

As previously discussed, the system 10 may include the patient sensor197. FIG. 5A provides a flowchart illustrating an embodiment of themethod where the system 10 includes the patient sensor 197. As shown,the method may include a step 400 of providing the remote caregiverinterface 198, the image sensor 193, the patient sensor 197, and thepatient support apparatus 100. The method may also include thepreviously described step 310 of selecting and executing the remotecontrol function and a step 420 of automatically altering the selectedremote control function based on the patient condition. As shown, step420 may include a step 430 of determining the patient condition.

It should be noted that step 420 and step 430 of FIG. 5A are similar tostep 320 and 330 of FIG. 3A. In both step 420 and step 320, the methodmay automatically alter the selected remote control function byautomatically aborting the selected remote control function, modifyingthe selected remote control function, or selecting a new remote controlfunction. Similarly, in both step 430 and step 330, the methoddetermines the patient condition. However, because the method in FIG. 5Aprovides the patient sensor 197 during step 400, there are somedifferences between steps 420 and 430 and steps 320 and 330.

For example, while the method of FIG. 3A may perform steps 311, 312′,and 316 to determine the patient condition during step 330, the methodof FIG. 5A may perform steps 411 and 412 to determine the patientcondition during step 430. During step 411, the method transmits thesensor input signal to the remote caregiver interface 198 and/or thecontroller 195 in response to sensing the state of the patient. Duringstep 412, the method determines the patient condition based on thesensor input signal. In one embodiment, the patient sensor 197 mayperform step 411. Furthermore, because the sensor input signal inputsignal is transmitted to the remote caregiver interface 198 and/or thecontroller 195, the remote caregiver interface 198 and/or the controller195 may determine the patient condition during step 412. In oneembodiment, the remote caregiver interface 198 and/or the controller 195may determine the patient condition by comparing the sensor input signalto a threshold value or by performing a calculation based on the sensorinput signal. For example, the sensor input signal may provide ameasurement of the patient's systolic and diastolic blood pressure. Theremote caregiver interface 198 and/or the controller 195 may determinethat the patient's condition is hypertensive if the systolic anddiastolic blood pressures exceed predetermined thresholds (e.g., 140 mmHg and 90 mm Hg, respectively). After the method determines the patientcondition during step 330, the method may proceed to the previouslydescribed step 317 and step 315′.

FIG. 6 provides a flowchart illustrating an embodiment of the methodwhere the method determines the patient condition during step 430 beforeselecting and executing the remote control function during step 310.Similar to the embodiment shown in FIG. 4 where step 330 triggers step310 step, here in FIG. 6 , step 430 may trigger step 310. Furthermore,the patient condition may be presented to the user of the remotecaregiver interface 198 after the patient condition is determined duringstep 430. The patient condition may be presented to the user of theremote caregiver interface 198 before step 310 or after step 312 of step310, but before step 313 of step 310. Furthermore, the method may alsonotify the caregiver 196 of the patient condition using a tactile,audio, or visual alert on the remote caregiver interface 198 after themethod determines the patient condition.

FIG. 7 is a schematic diagram illustrating the remote caregiverinterface 198, the local user interface 194, the image sensor 193, andthe speaker 185 of the patient support apparatus 100. As previouslydiscussed, and shown in FIG. 7 , the remote caregiver interface 198 mayreceive the user image data and the user audio data from the local userinterface 194. Furthermore, the remote caregiver interface 198 mayreceive the patient support apparatus image data from the image sensor193. Additionally, the remote caregiver interface 198 may capture thecaregiver audio data and the caregiver image data. As shown, the remotecaregiver interface 198 may transmit the caregiver audio data and thecaregiver image data to the local user interface 194. The remotecaregiver interface 198 may also transmit the caregiver audio data tothe speaker 185.

As such, in some embodiments, the remote caregiver interface 198 mayreceive the user image data and the user audio data from the local userinterface 194 and transmit the caregiver audio data to the speaker 185.Similarly, the remote caregiver interface 198 may receive the patientsupport apparatus image data from the image sensor 193 and transmit thecaregiver audio data to the speaker 185. In another embodiment, theremote caregiver interface 198 may receive the user image data and theuser audio data from the local user interface 194 and transmit thecaregiver audio data and the caregiver image data to the local userinterface 194. In such an embodiment, the caregiver 196 may see a faceof the patient and hear a voice of the patient via the remote caregiverinterface 198 and the patient may see a face of the caregiver 196 andhear a voice of the caregiver 196 via the local user interface 194. Assuch, the caregiver 196 and the patient may initiate a video conferencewith each other.

Furthermore, the remote caregiver interface 198 may transmit thecaregiver audio data to the local user interface 194 or the speaker 185without the caregiver image data. In this way, the caregiver 196 mayspeak to the patient via the local user interface 194 or the speaker 185without sending an image of himself or herself to the patient. Theremote caregiver interface 198 may also transmit the caregiver imagedata to the local user interface 194 without the caregiver audio data.In this way, the caregiver 196 may send an image of himself or herselfto the patient via the local user interface 194 without speaking to thepatient. Similarly, the local user interface 194 may only transmit theuser image data to the remote user interface 198 without the user audiodata or only transmit the user audio data to the remote caregiverinterface 198 without the user image data. In each of these embodiments,a “partial communication” is executed.

Additionally, it should be appreciated that the remote caregiverinterface 198 may transmit the caregiver audio data and/or the caregiverimage data without receiving the user image data, the user audio data,and/or the patient support apparatus image data. Similarly, the remotecaregiver interface 198 may receive the user image data, the user audiodata, and/or the patient support apparatus image data withouttransmitting the caregiver audio data and/or the caregiver image data.As follows, the local user interface 194 may receive the caregiver audiodata and/or the caregiver image data without transmitting the user imagedata and/or the user audio data. For example, the remote caregiverinterface 198 may transmit the caregiver audio data to the local userinterface 194 to provide the patient or another caregiver within avicinity of the patient support apparatus 100 with a command from thecaregiver 196. The local user interface 194 may also transmit the userimage data and/or the user audio data without receiving the caregiveraudio data and/or the caregiver image data. For example, the local userinterface 194 may transmit the user audio data to the remote caregiversuch that the patient may communicate with the caregiver 196 to providethe caregiver 196 with a request from the patient. In each of theseembodiments, a “one-way communication” is executed.

It should be noted that, at any point during the above describedmethods, the remote caregiver interface 198 may begin receiving the userimage data, the user audio data, and/or the patient support apparatusimage data. Furthermore, at any point during the above describedmethods, the remote caregiver interface 198 may transmit the caregiveraudio data and/or the caregiver image data. As such, the caregiver 196may, at any time during the method, view the patient, the face of thepatient, a person within a vicinity of the patient support apparatus100, or the patient support apparatus 100 itself, and/or hear the voiceof the patient or the voice of a person within the vicinity of thepatient support apparatus 100. Similarly, the patient may, at any timeduring the method, view the caregiver 196, the face of the caregiver196, and/or hear the voice of the caregiver 196. As such, the caregiver196 and the patient may communicate with one another at any time,allowing the caregiver 196 to better understand the patient's symptoms,to select an appropriate remote control function, to warn a patient ofan imminent remote control function, or to speak with the patient duringexecution of the remote control function.

FIG. 8 provides a flowchart illustrating a method of initiating thevideo conference based on the patient condition. As shown, the methodmay include step 330 or step 430 to determine the patient condition.Accordingly, the method may determine the patient condition by analyzingthe patient support apparatus image data from the image sensor 193during step 330 or by analyzing the sensor input signal from the patientsensor 197 during step 430. After determining the patient condition, themethod proceeds to a step 800 of initiating the video conference betweenthe local user interface 194 and the remote caregiver interface 198based on the patient condition.

It should be noted that, during step 330, the patient support apparatusimage data may be transmitted to the remote caregiver interface 198and/or the controller 195. Similarly, during step 430, the sensor inputsignal may be transmitted to the remote caregiver interface 198 and/orthe controller 195. As such, after the remote caregiver interface 198and/or the controller 195 may determine the patient condition, theremote caregiver interface 198 and/or the controller 195 may initiatethe video conference based on the patient condition. More explicitlystated, during step 800, the controller 195 or the remote caregiverinterface 198 may initiate the video conference between the local userinterface 194 and the remote caregiver interface 198.

As previously described, after determining the patient condition duringstep 330 or step 430, the method may initiate the video conferencebetween the local user interface 194 and the remote caregiver interface198 based on the patient condition during step 800. In some embodiments,the method may automatically initiate the video conference afterdetermining the patient condition. In further embodiments, the methodmay automatically initiate the video conference a period of time afterdetermining the patient condition. For example, if the method determinesthat the patient is experiencing cardiac arrest, the method mayautomatically initiate the video conference between the local userinterface 194 and the remote caregiver interface 198. In anotherexample, if the method determines that the patient is experiencingnausea, the method may automatically initiate the video conference 5minutes after the determination if the patient is still experiencingnausea.

In another embodiment, the method may determine the patient conditionduring step 330 or step 430 and transmit a signal representative of thepatient condition to the caregiver 196 via the remote caregiverinterface 198. In such an embodiment, the caregiver 196 may optionallyinitiate the video conference between the local user interface 194 andthe remote caregiver interface 198. For example, if the methoddetermines that the patient is suffering from dehydration, the methodmay allow the caregiver 196 to initiate the video conference between thelocal user interface 194 and the remote caregiver interface 198. Thecaregiver 196 may advise the patient to drink water.

In other embodiments, the method may automatically end the videoconference after determining the patient condition. In furtherembodiments, the method may automatically end the video conference aperiod of time after determining the patient condition. In still furtherembodiments, the method may also transmit the signal representative ofthe patient condition to the caregiver 196 via the remote caregiverinterface 198 and allow the caregiver 196 to end the video conference.For example, after the method determines that the patient has returnedto a stable state, the method may automatically end the videoconference, automatically end the video conference after 1 minute, orallow the caregiver 196 to end the video conference.

It should be noted that the method may automatically initiate or end thevideo conference, initiate or end the video conference after a period oftime, or allow the caregiver to initiate or end the video conferencebased on the patient condition. For example, if the patient condition isan emergency patient condition, such as cardiac arrest, or an allergicreaction, the method may automatically initiate the video conference. Inanother example, if the patient condition is lower risk patientcondition, such as discomfort or a fever, the video conference may allowthe caregiver to initiate the video conference based on the patientcondition. Similarly, if the patient condition is an emergency patientcondition, the method may allow the caregiver to end the videoconference even after the patient has returned to a stable state. If thepatient condition is a lower risk patient condition, the method mayautomatically end the video conference after the patient has returned toa stable state.

Furthermore, the method may execute a partial communication or a one-waycommunication, as defined above, based on the patient condition. Forexample, if the patient is suffering from dehydration, the method mayexecute a one-way communication by activating the speaker 185, allowingthe caregiver to instruct the patient to drink water. In anotherexample, if the patient is experiencing a sensitivity to light, themethod may execute a partial communication where the local userinterface 194 only receives the caregiver audio data and the screen ofthe local user interface 194 is not illuminated.

In the previously described methods, the methods may, at any time,receive the local control function from the local user interface 194. Aspreviously stated, the local control function may override the selectedremote control function. In such an embodiment, the local controlfunction may, at any time, abort the selected remote control function orselect a local control function to replace the selected remote controlfunction.

Furthermore, in the previously described methods, the methods mayperform a step indefinitely. For example, the method may continuouslycapture the patient support apparatus image data during step 311. Asanother example, the method may continuously transmit the patientsupport apparatus image data during step 312 and step 312′ andcontinuously transmit the sensor input signal during step 411. As yetanother example, the method may continuously determine the patientcondition during step 316 and step 412.

FIG. 9 illustrates an example embodiment of the remote caregiverinterface 198 and a graphical user interface 901 of the remote caregiverinterface 198. In FIG. 9 , the remote caregiver interface 198 is acellular phone, which may be used by a caregiver 196. As shown, thegraphical user interface 901 may provide a variety of remote controlfunctions 902 for selection by the caregiver 196. Furthermore, theremote caregiver interface 198 may provide measurements 904 of thepatient support apparatus 100, such as a height of the patient supportapparatus 100 or an incline of the patient support apparatus 100.Additionally, the graphical user interface may provide the patientsupport apparatus image data or a graphical representation 904 of thepatient support apparatus 100, which may update to reflect changes inthe patient support apparatus 100.

It will be further appreciated that the terms “include,” “includes,” and“including” have the same meaning as the terms “comprise,” “comprises,”and “comprising.” Moreover, it will be appreciated that terms such as“first,” “second,” “third,” and the like are used herein todifferentiate certain structural features and components for thenon-limiting, illustrative purposes of clarity and consistency.

Several configurations have been discussed in the foregoing description.However, the configurations discussed herein are not intended to beexhaustive or limit the invention to any particular form. Theterminology which has been used is intended to be in the nature of wordsof description rather than of limitation. Many modifications andvariations are possible in light of the above teachings and theinvention may be practiced otherwise than as specifically described.

The invention is intended to be defined in the independent claims, withspecific features laid out in the dependent claims, wherein thesubject-matter of a claim dependent from one independent claim can alsobe implemented in connection with another independent claim.

1. A system for remotely controlling a medical device based on imagedata, the system comprising: a patient support apparatus including asupport structure with a patient support surface to support a patient; amedical device including a controller coupled to a communicationnetwork, and an actuatable device operable to facilitate treatment ofthe patient; an image sensor coupled to the communication network andbeing configured to capture image data and to transmit the image data tothe controller; and a remote caregiver interface coupled to thecommunication network and configured to: display the image data forviewing by a user of the remote caregiver interface, receive a selectedremote control function from the user corresponding to operation of theactuatable device, and transmit an input signal corresponding to theselected remote control function to the controller of the medicaldevice, wherein the controller is configured to: determine a patientcondition, alter the selected remote control function based on thepatient condition; and transmit an output signal to the actuatabledevice to execute the altered remote control function to facilitatetreatment of the patient.
 2. The system as set forth in claim 1, whereinthe patient condition comprises a patient presence, a comfort indicationof the patient, a physiological state of the patient, or combinationsthereof.
 3. The system as set forth in claim 1, wherein the controlleris further configured to analyze the image data to determine the patientcondition.
 4. The system as set forth in claim 1, wherein the remotecaregiver interface is further configured to: analyze the image datafrom the image sensor to determine the patient condition, alter theselected remote control function based on the patient condition, andtransmit an input signal corresponding to the altered remote controlfunction to the controller; and wherein the controller is furtherconfigured to: transmit an output signal to the actuatable device toexecute the altered remote control function based on the input signalcorresponding to the altered remote control function.
 5. The system asset forth in claim 1, further comprising a patient sensor configured totransmit a sensor input signal in response to sensing a state of thepatient; and wherein the controller is further configured to receive thesensor input signal and to determine the patient condition based on thesensor input signal.
 6. The system as set forth in claim 5, wherein thepatient sensor is coupled to the communication network; wherein theremote caregiver interface is further configured to receive the sensorinput signal and determine the patient condition based on the sensorinput signal; wherein the remote caregiver interface is furtherconfigured to: alter the remote control function based on the patientcondition, and transmit an input signal corresponding to the alteredremote control function based on the patient condition; and wherein thecontroller is further configured to transmit the output signal to theactuatable device to execute the altered remote control function basedon the input signal corresponding to the altered remote controlfunction.
 7. The system as set forth in claim 1, wherein the imagesensor comprises an infrared image sensor, a visual light image sensor,or a combination thereof.
 8. The system as set forth in claim 1, whereinthe communication network is a wireless network.
 9. The system as setforth in claim 1, further comprising a local user interface configuredto transmit a selected local control function to the controller.
 10. Thesystem as set forth in claim 9, wherein the local user interface isconfigured to display a graphical user interface; and wherein the remotecaregiver interface is configured to display a graphical user interface,the graphical user interface on the remote caregiver interface beingidentical to the graphical user interface on the local user interface.11. The system as set forth in claim 9, wherein the local user interfaceis configured to display a graphical user interface; and wherein theremote caregiver interface is further configured to replicate at least aportion of the graphical user interface displayed on the local userinterface.
 12. The system as set forth in claim 1, wherein the imagesensor is coupled to the patient support apparatus.
 13. The system asset forth in claim 1, wherein image sensor is coupled to a supportstructure near the patient support apparatus.
 14. The system as setforth in claim 1, wherein the remote caregiver interface is a mobiledevice.
 15. The system as set forth in claim 1, wherein the remotecaregiver interface comprises a camera, the camera configured to captureimage data of the user of the remote caregiver interface.
 16. The systemas set forth in claim 15, further comprising a local user interfacecoupled to the communication network and being proximate to the patientsupport apparatus, the local user interface being configured to receivethe image data of the user from the remote caregiver interface.
 17. Thesystem as set forth in claim 16, wherein the remote caregiver interfaceis further configured to initiate a video conference with the local userinterface and wherein the local user interface is further configured toinitiate the video conference with the remote caregiver interface. 18.The system as set forth in claim 16, wherein one of the controller andthe remote caregiver interface is further configured to: determine apatient condition; and initiate a video conference with the local userinterface based on the patient condition.
 19. The system as set forth inclaim 1, wherein the actuatable device comprises a lighting device, atemperature device, a humidity device, or combinations thereof.
 20. Thesystem as set forth in claim 1, wherein the actuatable device comprisesa vibrational therapy device, a percussion therapy device, compressiontherapy device, a patient warming device, an electrical stimulationdevice, or combinations thereof.